View UT69R00012FCCG_7985933.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

standard products ut69r000 radhard microcontroller data sheet july 2002 q harvard architecture - 64k data space - 1m instruction space q high throughput engine - 2 clocks per instruction - 8 mips @ 16 mhz - static design q 15 levels of interrupts - 8 external user defined interrupts - machine error and power fail q two on-board 16-bit interval timers - timer a, 10 m s/bit - timer b, 100 m s/bit resolution q 8-bit software controlled output discrete bus q register- oriented architecture has 21 user-accessible registers - 16-bit or 32-bit register configurations q supports direct memory access (dma) system configuration q built-in 9600 baud uart q full military operating temperature range, -55 o c to +125 o c, in accordance with mil-prf-38535 for class q or v q typical radiation performance: - total dose: 1.0e6 rads(si) - sel immune >100 mev-cm 2 /mg - let th (0.25) = 60 mev-cm 2 /mg - saturated cross section (cm 2 ) per bit, 1.2e-7 - 2.3e-11 errors/bit-day, adams to 90% geosynchronous heavy ion q post-radiation ac/dc performance characteristics guaranteed by mil-std-883 method 1019 testing at 1.0e6 rads(si) q latchup immune 1.5-micron cmos, epitaxial, double-level-metal technology q packaging options: - 132-lead flatpack - 144-pin pingrid array (plus one index pin) 32 figure 1. ut69r000 functional block diagram oe we brq bgnt busy bgack nui1 nui2 nui3 state1 di1 di2 instruction data instruction address mchne1 bterr mchne2 mprot pfail i nt5 int6 int0-4 mrst 20 16 32 32 32 add mux memory control bus arbitra- tion proces- sor status processor control logic oscillator /clock general purpose registers oscin oscout sysclk id ic/ics acc shift reg temp dest 32 32 temp src bit reg 32 32 a mux b mux 32-bit alu 16 32 16 16 addr mux bus control uart tbr rbr timclk tes t uartout uartin tr tb im fr pi st sw 16 16 16 16 5 16 8 od(7:0) operand data dtack m/ io r/ wr ds operand address pipeline i/o mux inter- rupts 16 16 16 16
2 table of contents 1.0 introduction ..................................................................................................................... 4 1.1 general description .............................................................................................. 4 1.2 general operation ................................................................................................. 4 2.0 register file .................................................................................................................... 6 2.1 general purpose registers .................................................................................... 6 2.2 specialized registers ............................................................................................ 6 2.2.1 specialized register description ................................................................. 6 3.0 instruction port .............................................................................................................. 16 3.1 instruction port operations ................................................................................. 17 3.1.1 stri instruction bus cycle ....................................................................... 17 3.1.2 lri instruction bus cycle ......................................................................... 18 4.0 operand port ................................................................................................................. 19 4.1 operand bus cycle operation ............................................................................ 20 4.2 dma operation and bus arbitration .................................................................. 23 5.0 discrete input/output .................................................................................................... 25 5.1 output discrete bus ............................................................................................ 25 5.2 discrete inputs .................................................................................................... 26 6.0 interrupts ....................................................................................................................... 26 6.1 interrupt control ................................................................................................. 26 6.1.1 interrupt status ........................................................................................... 27 6.1.2 interrupt processing and vectoring ........................................................... 27 6.2 interrupt sources ................................................................................................. 28 6.3 interrupt hardware .............................................................................................. 28 6.4 interrupt latency ................................................................................................. 28 7.0 monitor ......................................................................................................................... 28 7.1 using the monitor ............................................................................................... 29 7.1.1 examine command .................................................................................... 33 7.1.2 modify command ...................................................................................... 33 7.1.3 continue command ................................................................................... 34 7.1.4 run command ........................................................................................... 34 8.0 internal uart operation ............................................................................................. 34 8.1 uart transmitter operation ............................................................................. 34 8.2 uart receiver operation .................................................................................. 35 9.0 programming interface .................................................................................................. 35 9.1 data formats ....................................................................................................... 35 9.2 instruction formats ............................................................................................. 36 9.3 addressing modes ............................................................................................... 37 9.4 data movement operations ................................................................................ 38 10.0 pin description .............................................................................................................. 39 11.0 absolute maximum ....................................................................................................... 46 12.0 recommended operating conditions ........................................................................... 46 13.0 dc electrical characteristics ........................................................................................ 47 14.0 ac electrical characteristics ........................................................................................ 48 15.0 packaging ...................................................................................................................... 58 16.0 ordering ........................................................................................................................ 60
3 ds r/ m/ dtack bgack busy bgnt brq mchne1 we oe mrst int6 int5 pfail int0 int1 int2 int3 int4 nui4 test exceptions interrupts/ instruction data port oscin oscout uartin uartout timclk ut69r000 ra19 ra18 ra17 ra16 ra15 ra14 ra13 ra12 ra11 ra10 ra9 ra8 ra7 ra6 ra5 ra4 ra3 ra2 ra1 ra0 nui1 nui3 bterr mchne2 mprot a0 a1 a2 a3 a4 a5 a6 a7 a8 a9 a10 a11 a12 a13 a14 a15 od7 od6 od5 od4 od3 od2 od1 sysclk instruction address bus processor status oscillator uart data bus memory address bus clock output bus control bus arbitration od0 figure 2. ut69r000 pin function diagram di1 di2 state1 rd0 - rd15 d0 - d15 operand operand nui2 discretes wr io
4 1.0 introduction the ut69r000 is a radiation-hardened high-performance microcontroller designed, manufactured, and tested to meet rigorous radiation environments. utmc designed and implemented the ut69r000 using an advanced radiation- hardened twin-well cmos process. the combination of radiation-hardness, high throughput, and low power consumption makes the ut69r000 ideal for high-speed systems in satellites, missiles, and avionics applications. 1.1 general description the ut69r000 is a versatile microcontroller designed to meet real-time control type applications. support functions often found external to a microprocessor are integrated within the microcontroller. functions include uart, interval timers, 10 external interrupt vectors, and a 8-bit output discrete bus. the ut69r000 core (machine) is a two port microcontroller that accesses instructions from a 1m x 16 instruction port; a second port (64k x 16 data port) is available for data storage. data transfer acknowledge allows the addition of wait states on the data port. the machine performs overlapping fetches and executes speeding instruction throughput. a 12 mhz operating clock frequency provides up to 6 mips of throughput. a later section of this data sheet expands on this concept. the ut69r000 architecture is based on 20 16-bit general purpose registers providing, the programmer with extensive register support. the ut69r000?s flexibility is enhanced by the concatenation of 16-bit registers into 32-bit registers. in addition, all registers are available for use as either the source or destination for any register operation. all ut69r000 circuitry is of static design. internal registers, counters, and latches do not require refresh as with dynamic circuit design. therefore the ut69r000 can operate from dc to the upper frequency limit of 16 mhz. this type of operation is especially useful in power critical applications such as satellites. the ut69r000 fully supports multiprocessor systems, dma, and complex bus arbitration. bus control passes among bus masters operating on the same bus. the bus master can be one of several ut69r000s or any other device requiring dma. the ut69r000 supports 15 levels of vectored interrupts. ten of these are external interrupts, all of which are user-definable. all interrupts are serviced in order of priority. the ut69r000?s three basic instruction formats support 16- bit and 32-bit instruction. the formats are register-to-register, register-to-literal, and register-to-long-immediate instructions. figure 3 shows the ut69r000?s general system architecture. 1.2 general operation the ut69r000 reduced instruction set consists of 35 separate instructions. most of these instructions execute in two clock cycles providing high-throughput. the ut69r000 has a harvard architecture which incorporates two address and two data buses. one set of address and data buses interface with instruction memory (instruction port) and the other interfaces with data memory (data port). the instruction port consists of a 20-bit address bus and 16-bit data bus. the maximum program length of any program is 1 mega-word. the data port consists of a 16-bit address and data bus, allowing access to 64k x 16 of data storage. the instruction port is dedicated to the storage of instruction code; however , two instructions exist that allow the instruction port manipulation by the machine. these instructions are the load register from instruction memory (lri) and store register to instruction memory (stri). 16 20 16 16 address figure 3. ut69r000 general system architecture control data memory instruction instruction instruction ut69r000 data memory data address
5 the ut69r000 begins operation by first generating an address on the instruction port; valid data (instruction) is then latched into the primary instruction register (pir). after the machine stores the instruction in the pir, the machine begins execution of the instruction in the instruction register (ir). if the present instruction in the ir requires only internal processing, the machine does not exercise the data bus. if the machine needs additional data to complete the instruction the machine begins arbitration for the data port. data port arbitration begins with the machine asserting the bus request ( brq ) signal. the machine samples the bus grant ( bgnt ) and bus busy ( busy ) signals on the falling edge of the clock (oscin). when the machine detects that the previous bus controller has relinquished control of the bus, the machine generates a bus grant acknowledge ( bgack ) signal signifying that it has taken control of the bus (i.e., data port). after the ut69r000 takes control of the bus, it generates valid address and data information. if the machine is interfacing to slow memory or other peripheral devices that require long memory-access times, the data transfer acknowledge ( dtack ) signal extends the memory cycle time. by holding off the assertion of dtack , the slow device lengthens the memory cycle until it can provide data for the machine. the ut69r000 controls the vectoring and prioritizing of interrupt service. internal logic selects one of 15 interrupt vectors, each interrupt vector is allocated four memory locations. use the four memory locations to store return from interrupt service address information along with the interrupt service routine?s location. the ut69r000 controls prioritizing of coincident interrupts. perform uart control and maintenance via input/output commands otr and inr. these commands allow the programmer to read uart status, and error information, as well as upload and download information to the receive and transmit buffers respectively. figure 4 shows an example of a system configuration. instruction data instruction add 16 20 nui3 user- defined system interrupts 8 uart i/f x c v r general purpose memory i/o device #1 i/o device #2 bus arbiter dma device #1 1553 i/f dma device #2 op add op data control 16 16 6 figure 4. the ut69r000 example system configuration 4 ut69r000 instruction memory can only be accessed by the ut69r000 instruction memory 1m x 16 internally pulled low serial i/o busy bgack brq bgnt oe we (max)
6 2.0 register file the ut69r000 has a register-oriented architecture. the registers within the machine fall into two categories, general purpose and specialized registers. all registers are accessible to the programmer through the instruction set. the programmer uses data from these registers to perform arithmetic and logical functions, alter program flow, detect various system and machine faults, determine machine status, control uart and timer functions, and for exception handling. 2.1 general purpose registers figure 5 shows the ut69r000?s 20 general purpose registers. the ut69r000 normally accesses these registers as single- word 16-bit registers although the machine can concatenate these registers into 32-bit double-word register pairs. when the programmer uses the general purpose registers as a double- word register pair, the most significant 16 bits of the 32-bit words are stored in the even-numbered register of the register pair. for instance, if a 32-bit word is stored in register pair xr6, the most significant word is stored in register r6 and the least significant word is stored in register r7. in addition to the 20 general purpose registers, the ut69r000 has a 32-bit accumulator (acc). the acc is normally a destination register, although under certain circumstances it can be the source register (inr rd, acc). the accumulator retains the most significant half of the product during a multiply instruction or the remainder during a divide operation. 2.2 specialized registers the ut69r000 has 13 special purpose registers. these registers control machine configuration, report status, and interrupts. below is a list of the special purpose registers. the values in the brackets indicate the power-up condition. 1. stack pointer register (sp) [xxxx (hex)] 2. system status register (status) [xxxx (hex)] 3. uart receiver buffer register (rcvr) [xx00 (hex)] 4. uart transmitter buffer register (txmt) [xx00 (hex)] 5. pending interrupt register (pi) [0000 (hex)] 6. fault register (ft) [0000 (hex)] 7. interrupt mask register (mk) [xxxx (hex)] 8. status/output discrete register (sw) [xxff (hex)] 9. instruction counter register (ic) [0000 (hex)] 10. instruction counter save register (ics) [xxxxx (hex)] 11. instruction register (ir) [0000 (hex)] 12. timer a (ta) [0000 (hex)] 13. timer b (tb) [0000 (hex)] the instruction set provides access to most of the special purpose registers. 2.2.1 register description stack pointer register the ut69r000 uses the 16-bit stack pointer register as an address pointer on push and pop instructions. the machine pre-increments (pop) and post-decrements (push) the stack pointer contents. the programmer loads and stores the sp by executing the inr and otr commands to the stack pointer. bit 15 is the most significant bit, the least significant bit is bit zero. system status register the system status register provides status information on the ut69r000?s internal operation, including status of the internal uart. the register is read via the inr rd, status instruction. bit definitions follow. figure 5. general register set concatenated 32-bit acc xr18 xr16 xr14 xr12 xr10 xr8 xr6 xr4 xr2 xr0 r19 r17 r15 r13 r11 r9 r7 r5 r3 r1 accumulator r6 r18 r16 r14 r12 r10 r8 r4 r2 r0 register pair 16 bits 16 bits 15 14 13 12 11 10 9 8 7 5 4 3 2 1 0 c p z n v j i m m e 6 o e r e f e p e c n t b e t e d r msb lsb figure 6. the system status register (status) e
7 bit number mnemonic description bit 15 c carry. this conditional status is set if a carry is generated or no borrow. [0] carry equations: c= ( dm * sm * rm ) + (dm * sm * rm) +(dm * sm * rm ) where: dm destination register most significant bit sm - source register most significant bit rm - result most significant bit (stored in destination register) bit 14 p positive. this conditional status is set if the result of an operation is positive. [0] positive equation: p = n * z bit 13 z zero. this conditional status is set if the result of an operation is negative. [0] zero equation: z = rm * rm-1 * rm-2 * r0 bit 12 n negative. this conditional status is set if the result of an operation is negative. [0] negative equation: n = rm bit 11 v overflow. this conditional status is set if the result when an overflow condition occurs. [0] overflow equation: v = ( dm * sm * rm ) + (dm * sm * rm) bit 10 j normalized. this conditional status is set as the result of a long instruction and the result is normalized. [0] normalized equation: j = (r32 xor r31) bit 9 ie interrupts enabled. this bit reflects whether interrupts are disabled or enabled. otr rd, enbl and otr rd, dsbl control this bit and function. [0] bit 8 mme discrete input 1. this bit reflects the input stimulus applied to the input pin. bit 7 re receiver error. this bit is the logical or combination of the oe, fe, and pe status bits. [0] bit 6 oe overrun error. when active, this bit indicates that at least one data word was lost because the data ready (dr bit 0 of the status register) signal was active twice consecutively without an inr rd, rcvr. [0]
8 uart receiver register (rcvr) the uart receiver buffer register (see figure 7) receives 9600-baud asynchronous serial data through the uartin input pin on the ut69r000. each serial data string contains an active-low start bit, eight data bits, an odd parity bit, and an active-high stop bit. figure 8 shows a single serial data string. while receiving a serial data string, the ut69r000 generates four status flags: data ready (dr), overrun error (oe), framing error (fe), and parity error (pe). the ut69r000 stores these bits in the system status register. receiver buffer register bits 15-8 are always low. bit numbers, 7 to 0 (rcd7 - rcd0) contain data the ut69r000 receives via the serial data port. rcd7 is the msb; rcd0 is the lsb. bit 5 fe framing error. when active, this bit indicates a stop bit was missing from the serial transmission string. cleared on next transmission. [0] bit 4 pe parity error. when active, this bit indicates the serial transmission was received with the incorrect parity. cleared on next transmission. [0] bit 3 cn discrete input 2. this bit reflects the input stimulus applied to the input pin. bit 2 tbe uart transmitter buffer empty. this bit indicates the transmitter buffer register is empty and ready for data. [0] bit 1 te uart transmitter empty. this bit is low while the uart is transmitting data and goes high when the transmission is complete. [0] bit 0 dr uart data ready. this active-high signal indicates the uart received a serial data word and this data is available. cleared on the execution of inr rd, rcvr. [0] bit number mnemonic description 15 14 13 12 11 10 9 8 7 5 4 3 2 1 0 0 5 0 4 0 3 0 2 0 1 0 0 7 0 6 0 6 r c d r c d r c d r c d r c d r c d r c d r c d msb lsb figure 7. the uart receiver buffer register (rcvr) 5 4 t 3 r 2 0 1 s t d 7 r c d r c d r c 6 r c d r c d r c d r c d r c d p a s t o figure 8. uart receiver single serial data string p r data flow
9 uart transmitter buffer register the ut69r000?s internal uart forms an 11-bit serial string by combining a start bit, the eight data bits from the transmitter buffer register, an odd parity bit, and a stop bit. figure 9 shows the composition of the serial data string. the ut69r000 transmits this serial string through the uartout pin at a rate of 9600 baud (timclk = 12mhz). the ut69r000?s internal uart has a double-buffered data transmission register (figure 10). the ut69r000 first loads the data for transmission into the transmitter buffer register. if the uart transmitter register is empty, data from the transmit buffer register automatically transfers to the uart transmitter register. at this time, the tbe bit goes active indicating more data may be loaded into the transmit buffer register. this double-buffering scheme allows contiguous transmission of serial data streams and also decreases the ut69r000?s required overhead for the uart interface. the ut69r000 loads the 8-bit transmit buffer register via the otr rd, txmt instruction. two status signals are associated with transmitting serial data. these signals are the uart transmitter buffer empty (tbe) and uart transmitter register empty (te). tbe and te are both active high and provide information on the status of double buffering the uart?s transmitted data. tbe and te are read from the system status register bits 2 and 1 respectively. 5 4 t 3 r 2 0 1 s t d 7 t x d t x d t x 6 t x d t x d t x d t x d t x d p a s t o figure 9. uart transmitter data string p r direction of data flow out of the ut69r000 figure 10. the ut69r000 uart double-buffered transmitter register register (otr) instruction tbr with an output data is loaded into the of the system status read from bit 1 transmitter register is status of the uart 8 register uart transmitter register (tbr) uart transmitter buffer 16 data bus the ut69r000?s internal from bit 2 tbr is read status of the data flow direction of t r t s 0 1 2 3 4 5 6 7 x t x t x t x t x t x t x t x t r a p p o t s 0 1 2 3 4 5 6 d x t d x t d x t d x t d x t d x t d x t 7 d x t d c d c d c d c d c d c d c d c of the system register status register
10 pending interrupt register the pending interrupt register (pi) contains information on pending interrupts attempting to vector the instruction counter register to a new location. software or hardware controls the pending interrupt register contents. any system interrupt, when active, sets the corresponding bit in the register. otr and inr instruction can also set, clear, and read the pending interrupt register (figure 11). instruction inr rd, pi stores the pi contents in the destination register. otr rd, pi loads the pi with the contents of the destination register. otr rd, rpi clears the pi register. for each bit set, to a logic one, in the destination register the corresponding pi bit is cleared. to clear the pi, first read the pi, then clear only the bits set to a logic one. reading, then clearing the pi prevents the inadvertent clearing of interrupts occurring during execution of an otr rd, rpi command. example: clear: inr rd, pi otr rd, rpi to generate a software interrupt clear the corresponding bit in the pi register before writing to the pi register. example: write: mov r1, 1000 (hex) otr r1, rpi otr r1, pi note: do not enable interrupts while the pi is non-zero. bit number mnemonic description bit 15 pwdn power fail bit 14 mche machine error interrupt bit 13 int0 external interrupt 0 bit 12 usr3 software interrupt 3 bit 11 fipo fix point overflow bit 10 usr2 software interrupt 2 bit 9 usr1 software interrupt 1 bit 8 tima timer a interrupt bit 7 int1 external interrupt 1 bit 6 timb timer b interrupt bit 5 int2 external interrupt 2 15 14 13 12 11 10 9 8 7 5 4 3 2 1 0 p w d n m c h e i n t o u s r 3 f i p o u s r 2 u s r t i m 6 t i m i n t i n t i n t i n t i n t i n t n / u msb lsb figure 11. the pending interrupt register (pi) 1 a 1 b 2 3 6 4 7
11 bit 4 int3 external interrupt 3 bit 3 int6 external interrupt 6 bit 2 int4 external interrupt 4 bit 1 int7 external interrupt 7 bit 0 nu not used* *note: the ut69r000 interrupt control hardware is designed such that the following sequence always occurs: the machine will vector to the lowest priority interrupt (vector 43chex) if interrupts are disabled after an interrupt is latche d into the pi register. interrupts are latched into the pi register on the falling edge of state1, interrupts are disabled on the falli ng edge of clock ck1 internal (rising edge of ck2). the ut69r000 vectors to address 43c (hex) during the fetch cycle of the command following the disable command. work around: vector 43c hex is not used as a normal interrupt; instead it is used to store the interrupt that occurred coinciden t with disabling of interrupts. the coincident interrupt is serviced after the interrupts are re-enabled by software. 43c: inr rd, ics jc x, pseudo nop pseudo: inr rd, pi ; read pi otr rd, rpi :clear pi otr rd, pi ;reset pi register, saves coincident interrupt call rd, rd ;return the interrupt service routine saves the interrupt that was coincident with the disable interrupt instruction. the ut69r000 will vector to that interrupt after interrupts are re-enabled. the interrupt service routine (@43c) does not affect the condition code flags .
12 fault register the ut69r000 uses the fault register (ft) to indicate the occurrence of a machine-error fault. a machine-error fault cannot be disabled. the ut69r000 uses the logical or combination of the 16 bit ft to generate a machine error interrupt, bit 14 of the pi. any bits in the ft the ut69r000 does not use are set to a logic zero. the ut69r000 reads, writes, and clears the ft with inr and otr instructions. fault register bits reflecting external pins are level sensitive; bit(s) cannot be reset until the external signal is negated. 15 14 13 12 11 10 9 8 7 5 4 3 2 1 0 mem parity i/o s y f 6 illegal t r e s built- msb lsb figure 12. the fault register (ft) prot instruc- tion and add fault in- test bit number mnemonic description bit 15 cmpf cpu memory protect fault. this bit indicates the ut69r000 has detected an access fault on the operand but (i.e., attempted access to write or read-protected memory). this bit is asserted only when the ut69r000 is controlling the operand data bus and the mprot input is asserted. [0] bit 14 dmpf dma memory protect fault. this bit indicates a dma device has detected an access fault (i.e., attempted access to write or read- protected memory). this bit is asserted when the ut69r000 is not controlling the operand data bus and the mprot input is asserted. bit 13 mchne2 machine error 2. this bit indicates that a user-defined machine error has occurred. reflects status of external input pin mchne2. bit 12 sft8 software error 8. this bit indicates that a user-defined software machine error has occurred. bit 11 sft7 software error 7. this bit indicates that a user-defined software machine error has occurred. bit 10 bterr2 i/o bus timer error. this bit indicates that a bus or time-out error occurred. the bit is set if the ut69r000 is performing an i/o access and bterr input is asserted. bit 9 sft6 software error 6. this bit indicates that a user-defined software machine error has occurred. bit 8 mchne1 machine error 1. this bit indicates that a user-defined machine error has occurred. it reflects the status of external input pin mchne1. bit 7 bterr1 memory bus timer error. this bit indicates that a bus or time-out error occurred. the bit is set if the ut69r000 is performing a memory access and the bterr input is asserted.
13 bit 6 sft6 software error 6. this bit indicates that a user-defined software machine error has occurred. bit 5 sft5 software error 5. this bit indicates that a user-defined software machine error has occurred. bit 4 sft4 software error 4. this bit indicates that a user-defined software machine error has occurred. bit 3 sft3 software error 3. this bit indicates that a user-defined software machine error has occurred. bit 2 sft2 software error 2. this bit indicates that a user-defined software machine error has occurred. bit 1 sft1 software error 1. this bit indicates that a user-defined software machine error has occurred. bit 0 sft0 software error 0. this bit indicates that a user-defined software machine error has occurred. bit number mnemonic description
14 interrupt mask register the interrupt mask register (mk) contains one mask bit for each of the 15 system interrupts. all bits in the mk are set or reset under software control, setting bits 15 and 10 has no effect on the ut69r000?s interrupt operation because these interrupts cannot be masked. the ut69r000 reads and writes the mk with instructions otr rd,mk and inr rd,mk. a logical one unmasks an interrupt; logic zero masks an interrupt. bit number mnemonic description bit 15 pwdn non-maskable interrupt bit 14 mche machine error interrupt bit 13 int0 external interrupt 0 bit 12 flpo software interrupt 3 bit 11 fipo fix point overflow bit 10 excl software interrupt 2 bit 9 flpn software interrupt 1 bit 8 tima timer a interrupt bit 7 int1 external interrupt 1 bit 6 timb timer b interrupt bit 5 int2 external interrupt 2 bit 4 int3 external interrupt 3 bit 3 ioli external interrupt 6 bit 2 i0l2 external interrupt 4 bit 1 int7 external interrupt 7 bit 0 nu not used (see note on page 11) 15 14 13 12 11 10 9 8 7 5 4 3 2 1 0 p w d n m c h e i n t o f l p o f i p o e x c l f l p t i m 6 t i m i n t i n t i n t i o l i n t i o l n / u msb lsb figure 13. the interrupt mask register (mk) u a b 1 2 3 1 4 2
15 status/output discrete register the status/output discrete register reports the c, p, z, and n bits of the system status register along with controlling the output discrete bus (od(7:0)). register bits c, p, z, and n contain the same information as the system status register bits 15, 14, 13, and 12. control of the output discrete bus is allowed via bit 0 through 7 of this register. use input and output instructions inr rd, sw and otr rd, sw to write and read this register. use this register to restore the condition codes after interrupt service routines. bit number mnemonic description bit 15 c carry bit 14 p positive bit 13 z zero bit 12 n negative bit 11 u/d user-defined bit 10 u/d user-defined bit 9 u/d user-defined bit 8 u/d user-defined bit 7 od7 output discrete 7 bit 6 od6 output discrete 6 bit 5 od5 output discrete 5 bit 4 od4 output discrete 4 bit 3 od3 output discrete 3 bit 2 od2 output discrete 2 bit 1 od1 output discrete 1 bit 0 od0 output discrete 0 15 14 13 12 11 10 9 8 7 5 4 3 2 1 0 condition user- 6 discrete msb lsb figure 14. the status/output discrete registers (sw) status (cs) defined
16 instruction counter and instruction register the ut69r000?s instruction port interface consists of a 20-bit instruction address and a 16-bit data bus. the instruction counter (ic) supplies the 20-bit address to memory. the instruction read from memory is then stored into the instruction register (ir, 16-bits wide). the ir consists of two sets of internal latches, a primary instruction register latch (pir, 16- bits wide) and the instruction register latch (irl, 16-bits wide). these two sets of latches allow the ut69r000 to perform overlapping memory fetch and execute cycles. this means the ut69r000 performs a delayed branch when the flow of the program is interrupted. a delayed branch implies that the ut69r000 fetches and executes the instruction following the branch condition before the ut69r000 executes the first instruction at the branch location. instruction counter save register the ut69r000 uses the instruction counter save register (ics) when servicing interrupts and branch instructions. when an interrupt or branch occurs, the ut69r000 saves the ic in the ics. read the ics immediately after entering the target routine to save the return location before any other ic save occurs. the ut69r000 reads the ics using input instruction inr xrd, ics. please note that the ics read requires a 32-bit wide register. timer a and timer b timer a and b registers are 16-bit binary counters. input/ output instructions start, halt, read, and write these counters. timer a resolution is 10 m s per bit, timer b has a resolution of 100 m s per bit (timclk at 12 mhz). each timer generates a time-out interrupt when the counter transitions from ffff (hex) to 0000 (hex). time intervals before interrupt are defined as the difference between the loaded value and 0000 (hex). for example, load timer a with the value fffe (hex), start timer a; an interrupt occurs 20 m s later as the timer transitions from ffff (hex) to 0000 (hex). the pending interrupt register reflects this time-out condition. modify the resolution of timer a and b by scaling the timclk input. for example, to decrease timer a resolution from 10 m s to 64 m s per bit, timclk is decreased to 1.88 mhz. 3.0 instruction port instruction port signals include a 20-bit address bus ra(19:0), a 16-bit data bus rd(15:0), and two control signals oe and we . during instruction and data fetch cycles, oe is asserted ( we negated). write operations to the port asserts we and negates oe . primarily designed for fast access of instruction information, the instruction port does not allow for the inclusion of wait states. the ut69r000 divides all operations into four distinct time periods (ck1 through ck4). these time periods are based on the processor clock. the ut69r000 performs a separate function during each of these four time periods. during ck1, the ut69r000 begins executing the instruction in the primary instruction register (pir). the instruction executed is the instruction the ut69r000 fetched during the previous bus cycle. also during ck1, the instruction address for the next instruction to fetch from memory becomes valid. (thus, the overlapping fetch and execute cycles of the ut69r000.) state1 output goes low, indicating the ut69r000 is executing an instruction. the ut69r000 begins variable width clock period ck2 after completing ck1. for 2 and 3 clock cycle instructions ck2 remains one-half clock cycle in length. during four clock cycle instructions ck2 is stretched to one and a half clock cycles. the following conditions extend time period ck2: (1) executing a stri instruction, (2) executing a lri instruction, or (3) executing any instruction access to the operand port. the ut69r000 also extends clock period ck2 for the operand port arbitration process. the ut69r000 samples the logical and combination of busy and inverted bgnt during ck2. if this combination is low, time period ck2 extends until the combination of the two signals is high, indicating the ut69r000 now controls the operand port. state1 output remains low for the entire ck2 time period. at the beginning of ck3, state1 goes high indicating the next instruction is being fetched from memory. the ut69r000?s operand address and data buses become active at the beginning of ck3 along with the bus grant acknowledge ( bgack ), m/ io , and r/ wr signals. data strobe ( ds ) asserts one clock cycle after the beginning of ck3, one and a half clock cycles after the start of ck4. following ck3 is variable length clock period ck4. the stretch of ck4 occurs during the following instruction executions: (1) executing a stri instruction, (2) executing a lri instruction, (3) executing any instruction with long immediate data (e.g., mov rd, ffffh), or (4) executing any operand port access. after time period ck4 starts, the transparent latches that make up the primary instruction register enable, allowing the ut69r000 to input the instruction from memory.
17 if the instruction being executed requires access to the operand bus, ds goes active. the ut69r000 samples the data transfer acknowledge ( dtack ) on the next and every subsequent rising edge of the processor clock. if dtack is not low, the ut69r000 extends time period ck4 until dtack becomes active or until an error condition is detected -- either bus error ( bterr ) or memory protect (mprot) becomes active. state1 remains high during the entire ck4 time period. figures 15, 16, and 17 show the timing relationships for ck1, ck2, ck3, and ck4 during 2, 3, and 4 clock cycle instructions. 3.1 instruction port operations most applications dedicate the instruction port to program information. for these applications we is always negated. the ut69r000 can manipulate the instruction port through instructions store register to instruction memory (stri, write access) and load register from instruction memory (lri, read access). section 3.1.1 and 3.1.2 review the stri and lri instructions. 3.1.1 stri instruction bus cycle during an stri instruction, instruction data moves from the ut69r000 to the instruction memory. figure 18 shows the timing diagram of the signal relationships for the ut69r000 during stri instruction bus cycle operation. before the ut69r00 executes the stri instruction, the system programmer must load the accumulator register with the address which will receive the data. when the acc is loaded with the address information, the ut69r000 can begin executing the stri instruction. executing the stri instruction begins when the falling edge of oscin signals the start of time period ck1. at the beginning of ck1, the data previously stored in the acc becomes a valid address on the instruction port address bus (ra(19:0)) and state1 output becomes active, indicating the ut69r000 is executing an instruction. oscin ck1 ck2 ck3 state1 execute fetch figure 15. machine cycle 1 (2 clock cycle instructions) ck4 ra(19:0) rd(15:0) valid address valid address valid address instruction data instruction data instruction data note: 1. examples of two clock cycle instructions include (internal operations): mov rd, rs add rd, rs
18 3.1.2 lri instruction bus cycle during an lri instruction, the ut69r000 moves the instruction data from the instruction memory to the ut69r000.figure 19 shows the timing diagram of the signal relationships for the ut69r000 during an lri instruction bus cycle. just as with the stri instruction, before the ut69r000 executes the lri instruction the system programmer must load the ut69r000?s accumulator with the address from which the data will be read. after the acc is loaded with the address information, lri instruction execution can take place. oscin ck1 ck2 ck3 ck4 figure 16. machine cycle 2 (3 clock cycle instructions) state1 execute fetch ra(19:0) rd(15:0) note: 1. examples of three clock cycle instructions include (operand port accesses): lr rd, rs str rd, rs status ds a(15:0) d(15:0) address valid data read control valid fetch address valid fetch instruction fetch address valid fetch instruction (m/io, r/ wr )
19 executing the lri instruction begins when the falling edge of oscin signals the start of time period ck1. at the beginning of ck1, the data previously stored in the acc becomes a valid address on the instruction port address bus (ra(19:0)) and state1 output becomes active indicating the ut69r000 is executing an instruction. the data on the data bus is read into the ut69r000 during time period ck2. the function of the remainder of the bus cycle (time periods ck3 and ck4) is the same as for other instructions. state1 is high, indicating the next instruction is being fetched from memory and is ready for execution during the next bus cycle. 4.0 operand port the ut69r000 operand data bus interface supports multiple processor and direct memory access (dma) configurations. the operand address bus a(15:0), data bus d(15:0), and memory control bus signals ( ds , r/ wr , and m/ io ) are ttl- compatible outputs that may be placed in a high-impedance state. these signals are only active during bus cycles when the ut69r000 is the current bus master. on other bus cycles, these signals enter a high-impedance state so an alternate bus master can control the port. oscin ck1 ck2 ck3 ck4 state1 figure 17. machine cycle 3 (4 clock cycle instructions) execute ra(19:0) rd(15:0) note: 1. examples of three clock cycle instructions include (long immediate accesses): mov rd, ffff (hex) add rd, ffff (hex) status ds a(15:0) d(15:0) address valid data read control valid fetch address valid fetch instruction immediate address immediate data fetch fetch address valid fetch instruction (m/io, r/ wr )
20 four signals make up the arbitration control bus -- bus request ( brq ), bus grant ( bgnt ), bus busy ( busy ), and bus grant acknowledge ( bgack ) . 4.1 operand bus cycle operation the timing diagrams in figures 20, 21, and 22 show signal relationships for the ut69r000 during an operand bus cycle operation. the ut69r000 performs one of four operations involving bus cycles on the operand buses: (1) memory read, (2) memory write, (3) i/o read, and (4) i/o write. the ut69r000 performs all four bus cycle operations similarly. the m/ io and r/ wr signals determine the precise type of bus cycle operation. for the following discussion, refer to figures 20, 21, and 22. when the operand bus arbitration process is complete and the ut69r000 controls the operand address and data buses, time period ck3 begins. the ut69r000 signal controls the operand port at the beginning of time period ck3 by asserting bgack . state1 transitions from low to high. at the same time, the following signals become valid: r/ wr , m/ io , and the operand address bus ra(15:0). control signals r/ wr and m/ io determine the direction and type of bus cycle taking place. one-half clock cycle after the beginning of time period ck4 or one full clock cycle after the start of time period ck3, ds goes active low. after ds has asserted, the ut69r000 samples the dtack input on every subsequent rising edge of oscin to determine the duration of ck4. a bus cycle terminates one- half clock cycle after the rising edge of oscin when the ut69r000 detects assertion of dtack . at this time, the operand address bus a (15:0) and the operand bus control signals (r/ wr , m/ io ) select the memory or i/o location from which the operand data is read, or to which the operand data is written. the ut69r000 also samples the and bterr inputs on the same rising edge of oscin. these two inputs indicate an error condition and terminate the current bus cycle. figure 18. stri instruction typical timing next data valid (rsn) stri next address address valid (acc) data risc address risc oscin ck1 ck2 ck3 ck4 instruction instruction state1 oe we mprot
21 after the ut69r000 recognizes the current bus cycle is finished, ds becomes inactive (transition from low to high) on the first rising edge of oscin after the end of time period ck4. the bus cycle completely ends one full clock cycle after the end of time period ck4, when bgack , r/ wr , and the operand address and data buses enter a high-impedance state. 4.2 dms operation and bus arbitration figure 22 shows the timing diagram of the signal relationships for the ut69r000 during a dma operation. for dma operations, multipurprocessor, and operand bus arbitration functions, the ut69r000 provides four active-low control signals for managing the operand bus and preventing bus contention. these signals are bus request ( brq , bus grant ( bgnt ), bus busy ( busy ), and bus grant acknowledge ( bgack ). each of the four bus control signals provides a specific function for controlling operand bus operation. the function of each of the four signals is given below. bus request ( brq ) the ut69r000 generates brq to indicate a request to use the operand buses. the ut69r000 retains control of the buses by keeping the bgack signal active until it no longer requires the buses. bus grant ( bgnt ) an external arbitrator generates this input indicating to the ut69r000 that it has the highest priority. this informs the ut69r000 to control the operand buses as soon as the present bus master relinquishes bus control by asserting busy . bus busy ( busy ) another bus master generates busy input to the ut69r000, indicating another bus master is using the bus. bus grant acknowledge ( bgack ) the ut69r000 generates this signal to indicate it is the present bus master. bgack enters a high-impedance state when the ut69r000 gives up control of the operand buses. ck4 ck3 ck2 ck1 oscin risc address risc data address valid (acc) next address lri data valid (rsn) next figure 19. lri instruction typical timing instruction instruction state1 oe we
22 on these falling edges oscin ck1 ck2 ck3 ck4 instruction address instruction data executing the risc instr. fetched during the previous cycle primary instr. register latches are open fetching the risc instr. to be executed during the next cycle valid instruction address valid instruction data operand data operand address control valid operand address valid operand data valid bus control signals figure 20. typical ut69r000 bus cycle with extended clock cycles rd(15:0) ra(15:0) a(15:0) d(15:0) brq bgnt busy bgack ds state1 bgnt and busy are sampled
23 data operand address operand control ck4 ck3 ck2 ck1 oscin (1) address valid data valid (2) figure 21. typical ut69r000 data bus cycle operation notes: state brq bgnt bgack ds r/ wr dtack 1. dtack must be active by this edge to avoid wait states. 2. dtack is sampled by the rising edges of oscin.
24 data operand address operand control ck4 ck3 ck2 ck1 oscin address valid data valid (1) figure 22. typical ut69r000 dma bus cycle note: 1. bgnt is sampled by the falling edges of oscin. wait states are inserted until bgnt is low and busy is high. dtack ds bgack bgnt brq state1 r/ wr
25 the ut69r000 requests control of the operand buses at the beginning of time period ck2 by asserting brq . on every subsequent falling edge of oscin, the ut69r000 samples the bgnt and busy inputs. when the ut69r000 detects on the falling edge of oscin that bgnt has gone low and busy has gone high, the ut69r000 is the new bus master and can now control the operand buses. the ut69r000 locks out any other bus master from controlling the operand buses by asserting bgack at the beginning of time period ck3 and holding bgack active until it is ready to relinquish control of the operand buses. the ut69r000 holds the bgack signal active until the beginning of the ck3 time period of the next bus cycle when the ut69r000 no longer controls the operand buses. 5.0 discrete input/output to control external hardware and receive external information, the ut69r000 has an 8-bit output discrete bus and two discrete inputs. the discrete input function allows for easy gathering of information from the subsystem. the output discrete bus allows the ut69r000 to control subsystems via a combination of hardware and software. 5.1 output discrete bus the ut69r000 has eight user-defined output discretes (od(7:0)). output register instruction otr rd,sw governs the logic state of each output discrete. the status/output discrete register reflects the state of the output discretes. software can read the contents of this register by executing. the input register instruction inr rd,sw. ra(19:0) rd(15:0) od(7:0) oscin ck1 ck2 ck3 ck4 state1 execute fetch execute otr ra,sw xxxx (hex) otr ra, sw figure 23. output discrete bus timing od(7:0) valid
26 useful in the control of external subsystem hardware, the output discrete function is fully static and remains unchanged until rewritten. outputs can drive standard (i.e., sink or source) ttl loads. these outputs three-state on the assertion of the test input pin. figure 23 shows the timing relationships for a write to the output discrete bus. 5.2 discrete inputs status register bits di1 and di2, bits 8 and 3 respectively, reflect the stimulus applied to the input pins. in a system application the software would make decisions based on the state (i.e., logic one or zero) of either or both of these bits. the system software would poll the status register by executing an input register instruction inr rd,sw; the software then proceeds to perform a test bit on the appropriate bit (i.e., 3 or 8). the result of the test bit determines the next task performed by the software. section 7.0 discusses an example of using a discrete input to control program for entering the monitor program. both di1 and di2 input buffers have pull-down resistors and can float if not in use. 6.0 interrupts 6.0 interrupts the ut69r000 has 15 levels of internal interrupt prioritizing. upon the occurrence of an enabled non-masked interrupt, the ut69r000 program flow (i.e., instruction counter) transfers to the appropriate interrupt vector. the interrupt vector points to an interrupt service routine. after completing the interrupt service routine the program flow is returned to the main program location. table 1 shows a list of ut69r000 interrupts. 6.1 interrupt control the pending interrupt register, mask register, status register, and fault register control and report interrupt processing. these registers contain the following interrupt information: - interrupt events (pi) - interrupt status, masked versus unmasked (mk) - interrupt status, enabled versus disabled (status bit 9) - machine error interrupts (ft) table 1. interrupt definitions interrupt number 0 (highest priority) 1 2 3 4 5 6 7 8 9 10 11 12 description power-down interrupt.cannot be masked or disabled. machine error. cannot bedisabled. int0. external user interrupt. software interrupt (usr3) fixed-point overflow.(v bit) software interrupt (usr2) software interrupt (usr1) timer a (if implemented). int1. external user interrupt. timer b (if implemented). int2. external user interrupt. int3. external user interrupt. int4. external user interrupt. int6. external user interrupt. 13 14 (lowest priority) int5. external user interrupt.
27 the interrupt architecture allows for the disabling and masking of certain interrupts. output register instruction otr rd,enbl and otr rd,dsbl control the disable and enable of interrupts. the content of the rd register is a ?don?t care? for these commands. status register bit 9 reflects the state of interrupts (i.e., enabled or disabled). the mask register provides the ability to mask the service of user selected interrupts. interrupts awaiting service are reflected in the pi register. execution of input register and output register instructions inr rd,pi, otr rd,pi and otr rd,rpi read, write, and clear the pi register. to latch an interrupt into the pi register the corresponding bit must be a logic zero before the event occurs. an integral part of interrupt service should include the clearing of the appropriate bit in the pi register. section 2.2.1 shows an example of clearing the pi register. 6.1.1 interrupt status the architecture of the ut69r000 allows for the disabling and masking of interrupts. if the software cannot support interrupt service the software can disable (i.e., not recognize) interrupts. the disable feature will prevent the servicing of all interrupts with the exception of power fail ( pfail ) and software interrupt (usr2). the ut69r000 will log these interrupts into the pi register but does not alter program flow to the interrupt vector. re-enabling interrupts with a non-zero pi register will result in the ut69r000 vectoring to the highest priority interrupt. to prevent the service of these interrupt clear the pi register before re-enabling interrupts. the mask feature allows the software to select particular interrupts for service while masking others. the selection of interrupts, via the mask feature, for service is controlled through the mk register. input register and output register instructions inr rd,mk and otr rd,mk read and write the mk register. the mask feature prevents the servicing of all interrupts with the exception of pfail and usr2. similiar to the disable feature, unmasking and interrupt with a non-zero pi register results in the vectoring to the appropriate interrupt vector. writing a logical zero into a mask register bit location will prevent the recognition of the specific interrupt (i.e., mask). to un-mask all interrupts write ffff (hex) to the mk register. to enable the ut69r000 interrupts architecture the software program enables interrupts by executing instruction otr rd,enbl, followed by a write to the mask register, otr rd,mk. interrupts are enabled and disabled on the falling edge of internal clock cycle ck1 (rising edge of ck2). 6.1.2 interrupt processing and vectors the occurrence of an enabled and non-masked interrupts results in the altering of program flow. interrupt processing begins by saving the present instruction counter register (ic) in the instruction counter save register (ics) followed by automatic disabling of all interrupts (status register bit 9 equals logic 0). the ut69r000 then loads the designated interrupt vector location into the instruction counter. the ut69r000 begins interrupt service by executing the code residing at the interrupt vector location. interrupt vectors reside from memory location 400 (hex) to 43c (hex). each interrupt is assigned a vector with four memory locations (see table 2). these four memory locations allow for storage of the instruction counter save register (ics) and a jump (jc), branch (br), or call (call) to the interrupt service routine. an example is shown below. isr0_int0: 408 (hex) inr xr0, ics 409 (hex) call xr18, isr0 40a (hex) isr0 40b (hex) nop table 2. interrupt instruction counter load location interrupt number location (hex) mask- (y/n) can user disable (y/n) able 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15* 0400 0404 0408 040c 0410 0414 0418 041c 0420 0424 0428 042c 0430 0434 0438 043c n y y y y n y y y y y y y y y y n n y y y n y y y y y y y y y y * see note on page 11.
28 read the ics register with an input register instruction inr rd,ics before interrupts are re-enabled or before executing a program branch to assure that the return address in the ics is not overwritten. the call instruction saves the ic into the ics register and overwrites the interrupt return address with the call return address. similarly, if the interrupts are re- enabled before the interrupt return address is read from the ics, the occurrence of a new interrupt causes the old return address to be overwritten. it is suggested for call instructions the software reserve register pair xr16 for ics storage; for interrupts the software reserve register pair xr18 for ics storage. when nested calls or interrupts are encountered, the address values stored in register pairs xr16 and xx18, respectively, must be stored in system memory to provide the ut69r000 with full return information. 6.2 interrupt sources interrupt sources include nine externally generated hardware interrupts, two internally generated hardware interrupts, and four internally generated software interrupts. external interrupts include: int (6:0), mchne(2:1), pfail , bterr , mprot, and mpar. internal hardware interrupts include tima and timb. software interrupts include usr(3:1) and fipo. user-defined hardware interrupts int (6:0) are available to signal the occurrence of events which require special action by the ut69r000. user-defined interrupts are entered into pi register bits 2, 8, 10, 11, 12, 13, and 14. internal hardware interrupts tima and timb signal the wrap-around of either of these 16-bit counters from ffff (hex) to 0000 (hex). machine error interrupts mchne(2:1), bterr , mprot, and mpar designate machine error interrupts. the ut69r000 enters machine error interrupts into the fault register, the logical or of all fault register bits generates the stimulus to control bit 14 of the pi register. on the occurrence of a machine error interupt the host examines the fault register to determine the specific event that generated the interrupt. input register and output register instructions inr rd,ft, otr rd,ft, and otr rd,rft read, write, and clear the fault register. clear the fault register before clearing the pi register. generate software interrupts by executing an output register instruction otr rd,pi. user-defined software interrupts include usr3, usr2, and usr1. a fourth software interrupt includes fipo, fixed-point overflow. when enabled and not masked interrupt fipo signals the assertion of condition code bit v to a logical one. generate user-defined interrupt usr3, usr2, and usr1 by writing to the pi register. please note; clear the specific bit in the pi register before attempting to generate a software interrupt. 6.3 interrupt hardware all the ut69r000 external interrupts are level triggered. interrupts int (6:0) and pfail are sampled on the rising edge of the oscin and latched into the pi register on the falling edge of state1 (rising edge of ck1). the minimum pulse width for these inputs is 500 ns. machine error interrupts mchne(2:1), bterr , mpar, and mprot provide stimulus to the pi register through an s-r flip-flop. the architecture requires removal of the interrupt signal before the fault register (ft) and pi register can be cleared. if the ft and pi register is cleared while the interrupt input is asserted the specific ft and pi register bit is re- asserted. 6.4 interrupt latency figures 24, 25, and 26 display the latency associated with servicing of interrupts. when an interrupt is sampled into the ut69r000 before the falling edge of state1 (figure 24) interrupt service begins during the following execute machine cycle ( state1 low). if the interrupt is sampled into the ut69r000 after the falling edge of state1 (figure 26) interrupt service is delayed one execution cycle. interrupts are first sampled into the device and then latched into the pi register. when the interrupt is latched coincident with the fetch and execution of a call instruction the interrupt latency increases. figure 25 shows interrupt latency associated to the call instruction. the increase in interrupt latency is due to the temporary disable of the latching of interrupts into the pi register. this temporary disable is due to the fetch of the call instruction. the disable is necessary to allow for the ut69r000 to execute the call instruction before servicing the interrupt.7.0 monitor 7.0 monitor communication between the ut69r000 and a dumb terminal or irsim is established via a monitor program written to support the internal uart. when operating in the monitor mode the programmer can (1) examine and modify the ut69r000?s internal registers; (2) examine and modify the contents of the operand port memory; (3) examine and modify the contents of i/o subsystems; (4) control program execution. utmc offers a monitor shell program for the ut69r000. the software programmer can tailor the monitor program to meet specific application. assertion of a discrete input can signal the ut69r000 to enter the monitor mode of operation. to perform this function the application software polls the status register looking for the assertion (i.e., transition to logic one) of the appropriate discrete input. the ut69r000 then enters the monitor program via a call or br instruction. interrupts can also be used to
29 access the monitor program. an example of this technique is accessing the monitor on a specific condition. a specific interrupt event (e.g., memory access location 100) can generate a hardware interrupt to the pfail input. accessing the monitor allows the software programmer to evaluate the state of the ut69r000 and system (i.e., memory or i/o subsystem). figures 27 and 28 show an example. 7.1 using the monitor when the ut69r000 enters the monitor mode, it begins executing the monitor program stored in the instruction port. the ut69r000 initially sets its internal uart as the default monitor interface. to control the ut69r000 with the monitor, the user simply transmits a predefined set of ascii characters over the serial data port. the list of the predefined ascii characters meaningful to the ut69r000?s monitor mode are described in detail in the following sections. the ut69r000 can receive these monitor control commands with its internal uart, decode them, and then take the appropriate action. all ascii characters must be capitalized for the ut69r000 to recognize them. the four primary ascii control characters are e, m, c, and r. these control characters permit the system user to examine or modify instruction memory, operand memory, external i/o, and internal registers, continue execution, and run from a set starting location. oscin ck1 ck2 ck3 ck4 execute (nop) pir open pir close execute interrupt service commands primary instruction register (pir) fetch (nop) state ra(19:0) rd(15:0) int interrupt address valid interrupt instruction valid figure 24. interrupt timing assumes: 1. interrupts enabled at time zero. 2. no mask bits set at time zero. do not care field do not care field #
30 oscin ck1 ck2 ck3 ck4 execute (call) execute (nop) interrupts disabled due to fetch of call or jmp instruction fetch (call) interrupt address valid interrupt instruction valid ra(19:0) rd(15:0) fetch (nop) execute interrupt service commands figure 25. interrupt timing state1 int assumes: 1. interrupts enabled at time zero. 2. no mask bits set at time zero. do not care field do not care field #
31 oscin ck1 ck2 ck3 ck4 execute (enop) pir open pir close ra(19:0) rd(15:0) execute interrupt service commands primary instruction register (pir) fetch (nop) fetch (inr) execute (inr) interrupt address valid interrupt instruction valid figure 26. interupt timing state1 int assumes: 1. interrupts enabled at time zero. 2. no mask bits set at time zero. do not care field do not care field #
32 program code xxxxx(hex) xxxxx(hex) external hardware interrupt or output discrete: ic ics ic interrupt map address 4xx (hex) interrupt service routine: 4xx (hex) inr xr16, ics ;save ics 4xx (hex) call xr18, monitor ; monitor code 4xx (hex) monitor 4xx (hex) nop figure 27. monitor operation monitor mode ut69r000 uart port console terminal ut69r000 monitor rs-232 port examine (ei, eo, ee, er) continue (c0, c1, c2, c3) run (r0, r1, r2, r3) modify (mi, mo, me, mr) figure 28. monitor mode operation
33 7.1.1 examine command the examine command has four variations: (1) eixxxx - the examine instruction memory command. this command permits the user to examine any memory location within the 64k instruction memory space. the ei command is followed by the 16-bit hex address, above as ?xxxx,? of the memory location to examine. valid characters for the instruction address field (xxxx) are 0- 9 and a-f. the user can examine consecutive memory locations by repeatedly entering space characters. the monitor continues to display the contents of contiguous memory locations until any non-space character is received. when the monitor receives a non-space character, it terminates ei command execution and waits for the next valid monitor command. (2) eoxxxx - the examine operand memory command. this command works exactly the same as the ei command except that the user can now examine operand memory. (3) eexxxx - the examine external (i/o) command. this command works exactly the same as the ei and eo commands except that the user can now examine any external i/o location. (4) er - the examine register command. the examine register command allows the user to look at most of the ut69r000?s internal registers. after the ut69r000 has received the er command, it displays the contents of register r0. the user can examine additional registers by repeatedly transmitting space characters to the ut69r000. the monitor displays the registers one after another in the following order: r0 through r15, status/output discrete register (sw), pending interrupt register (pi), interrupt mask register (mk), fault register (ft), timer a (ta) and timer b (tb). the ut69r000 continues to display its registers until the ut69r000 receives a non-space character oruntil the ut69r000 has displayed the complete list of registers. at this time the ut69r000 terminates the er command and waits for the next valid monitor command. 7.1.2 modify command the modify command has four variations: (1) mixxxx,vvvv - the modify instruction memory command. this command permits the user to modify any memory location within the 64k instruction memory space. the mi command is followed by the 16-bit hex address denoted above as ?xxxx,? of the memory location to examine and the 16 bit hex value denoted above as ?vvvv,? the user wishes to place in this memory location. valid characters for the instruction address field (xxxx) and value field (vvvv) are 0-9 and a-f. the user can modify consecutive memory locations by entering multiple 16-bit values in the mi command. the mi command would then take the form: mixxxx,vvvv,vvvv,...,vvvv where the user can enter as many new values as desired. the commas are optional as delimiters. the ut69r000 now modifies instruction memory starting at the given address (xxxx) and continues to modify memory until all new values are in memory. (2) moxxxx,vvvv - the modify operand memory command. this command works exactly the same as the mi command except that the user can now modify operand memory. the form of the mo command to alter multiple operand memory locations is: moxxxx,vvvv,vvvv,...,vvvv. (3) mexxxx,vvvv - the modify external i/o command. this command works exactly the same as the mi and mo commands except that the user can now modify any external i/o location. the form of the me command to alter multiple external i/o locations is: mexxxx,vvvv,vvvv,...,vvvv. (4) mrrr,vvvv - the modify register command. the modify register command allows the user to modify most of the ut69r000?s internal registers. the mr command is followed by an 8-bit register id code, denoted as rr, and a 16-bit value, denoted as vvvv. table 4 lists the register ids that the ut69r000 recognizes. valid characters for the register id field (xxxx) and value fields (vvvv) are 0-9 and a-f. the user can use only one mr command to modify one ut69r000 register. modifying additional registers requires transmitting a separate mr command for each change.
34 7.1.3 continue command the continue execution command allows the user to resume program execution from the point where the monitor mode of operation was entered. the continue execution command takes the form: c0-resume execution with timers a and b halted. c1- resume execution with timer a on and timer b off. c2 - resume execution with timer a off and timer b on. c3- resume execution with timers a and b on. 7.1.4 run command the run from memory location command allows the user to start program execution from any point within the 1m port space. this command takes the form rxxxxn where ?xxxxx? denotes the 20-bit starting address. valid characters for the address field (xxxx) are 0-9 and a-f. the value n is either 0,1,2, or 3 and is defined: 0 - resume execution with timers a and b halted. 1 - resume execution with timer a on and timer b off. 2 - resume execution with timer a off and timer b on. 3 - resume execution with timers a and b on. 8.0 uart operation the ut69r000 has an internal uart. figure 29 shows a diagram of the ut69r000 connected to a serial bus. the uart operates at a fixed frequency of 9600 baud with eight bits, one stop bit, and odd parity. the idle state for the uart is logic zero. the timclk input fixes the baud rate of the uart (9600 baud at timclk equal to 12 mhz). timclk also controls the frequency of the internal timers (ta and tb). the status of the uart is read from the system status register (status) bits 7 through 0. 8.1 uart transmitter operation the transmitter portion of the ut69r000?s uart is a double- buffered configuration consisting of a transmitter register and a transmitter buffer register. the transmitter register contains the serial data stream the ut69r000 is currently transmitting through the uart; the transmitter buffer register contains the next message to transmit through the uart. the system programmer reads the status of the transmitter register from bit 1 (te) of the status and the status of the transmitter buffer register from bit 2 (tbe) of the status register. if bit 2 of the status register is a logical one, the uart transmitter buffer is ready for data, once loaded with data, bit 2 transitions to a logical zero. bit 1 is a logical zero during serial transmission and transitions to a logical one when transmission from the transmitter register is complete. the status register is read using input register instruction inr rd,status. to initiate a serial data transmission, the system designer must first load the data to transmit into the transmitter buffer register with the output register instruction otr rd, txmt. this instruction loads the least significant byte of the source register specified in the instruction into the transmitter buffer register. at this time, tbe goes low and the ut69r000 automatically transfers the data word into the transmitter register. after the transfer is complete, te goes low and tbe transition to a logical one indicating a serial transmission is about to begin and the next data word can be loaded into the transmitter buffer register. figure 29. serial data bus interface to the ut69r000 and odd parity one stop bit eight data bits, 9600 baud serial rs-232 bus x0106- rcvr bus serial drvr bus serial ut69r000 for uart 12 mhz i/p timclk uartin uartout
35 this double-buffering process allows transmitting contiguous serial data streams. the process of alternately loading the transmitter buffer register with new data and then reading the transmitter status from the status register continues until completion of all serial transmission. an example of uart transmitter software follows: write_uart: inr r11, status tbr r11, 1dh br eq, write_uart nop inr r15, txmt 8.2 uart receiver operation the ut69r000?s internal uart has one register associated with the receive function. this register is the uart receiver buffer register (rbr). the least significant byte of the rcvr contains the received serial data. the status register contains error information about the serial data in the receiver. four error bits reflect information status, bit 7 (receiver error, re), which is the logical or combination of the other three error bits; bit 6 (overrun error, oe); bit 5 (framing error, fe); bit 4 (parity error, pe). an additional status bit for the receiver is the data ready (dr) bit. dr is the least significant bit of the status register. the ut69r000 is ready to receive serial data through the internal uart, it must poll the status register to determine when the data ready (dr) bit transitions from a logical zero to logical one to signal the uart has indeed received a serial transmission. when dr equals a logic one, the software reads the receiver by executing and input register operation inr rd, rcvr. the inr instruction takes the eight bits of received data in the and places this data in the least significant byte of the destination register (rd) specified in the instruction. when the ut69r000 is finished executing the input register instruction, the software can then determine the validity of the message by testing the re bit. after the software has checked for a valid message, the data is stored. if the ut69r000 is to receive more data through the uart, the software must return to polling the status register to determine the reception of the next valid serial transmission. the input register instruction inr rd, rcvr clears the dr bit. an example of receiver software follows: read_uart: inr r11, status tbr r11, 1fh br eq, read_uart nop otr r15, rcvr 9.0 9.0 programming interface 9.1 data formats the ut69r000 instruction set supports 16-bit integer single- precision data and 32-bit integer double-precision data. all data is in 2?s complement representation. the ut69r000 represents the fixed-point data formats as a 2?s complement integer with the msb as the sign bit (figures 30a and 30b). operand size the ut69r000?s instruction set supports three operand sizes: (1) byte (eight bits); (2) word (16 bits); and (3) long word (32 bit). byte operands are only allowed with byte instructions. all other instructions support word and long-word operands. organization of data in general purpose registers all 20 of the ut69r000?s general purpose data registers support bit, byte, and word operations. when the system programmer specifies a byte operation in a specific instruction, the instruction expects to find the byte of operand data in the least significant eight bits of the data register. the least significant bit of each of the data registers is bit 0 and the most significant bit of each of the data registers is bit 15. any one of the data registers may be the source or destination for the operand. for long-word operands, the ut69r000 organizes the 20 general purpose data registers as 10 even/odd register pairs. the even-numbered register of the register pair contains the most significant word. all register pairs may be the source or destination operands. 14 0 figure 30a. single-precision fixed-point data figure 30b. double-precision fixed-point data 15 sign data lsb msb sign msb lsb (msh) (lsh) 31 30 16 15 0
36 special purpose data registers in addition to the 20 general purpose data registers, the ut69r000 has three special purpose data registers: (1) the accumulator (acc); (2) the stack pointer (sp); and (3) the instruction counter save register (ics). the accumulator (acc) is a 32-bit register used only with multiply, divide, extended shift, load register from instruction memory (lri), and store register to instruction memory (stri) instructions. for multiply instructions, the acc retains the most significant half of the product, and for divide instructions, the acc retains the remainder. for lri and stri instructions, the acc contains the instruction memory pointer. note that the acc can be used as a general purpose register for most operations. the stack pointer (sp) is a 16-bit register usable only with pop and push instructions. the instruction counter save (ics) register is a 20-bit register used during calls, jumps, and interrupts. register notation the ut69r000?s instruction descriptions contain a definition of the register transfer language (rtl) that the assembler uses to describe how the instructions operate. the rtl description of the ut69r000?s internal registers is as follows: rs n -- s ource register where n specifies the register number. rd n -- destination register where n specifies the register number. xrs n -- long-data source register where n specifies the register number. xrd n -- long-data destination register where n specifies the register number. ic -- instruction counter sp -- stack pointer acc -- 32 bit accumulator ics -- instruction counter store register @rsn -- data register indirect where n specifies the register number @sp -- stack pointer indirect # -- immediate data @# -- immediate data indirect 9.2 instruction formats the ut69r000 has three instruction formats (figure 32): (1) register-to-register; (2) register-to-short immediate; and (3) register-to-immediate. all the ut69r000?s instructions are either word (16-bit) or long-word (32-bit) in length. the only time the ut69r000 uses the long-word instruction format is for the immediate source operand address mode. the bits in the instructions are defined as follows: m: instruction mode bit. when m = 1, the ut69r000 interprets the instruction source field as a five-bit literal value. if m = 0, the ut69r000 uses the instruction source field to specify the source register for the instruction. opcode: this field is the five-bit opcode the ut69r000 uses to decode the instruction into a machine operation. 0 4 5 9 10 14 15 figure 31b. register to-short immediate 0 4 5 9 10 14 15 figure 31a. register to-register instruction figure 31c. register immediate instruction format msb lsb mode opcode destination source 0 xxxxx rd rs mode opcode destination source msb lsb 1 xxxxx rd immediate mode msb opcode destination source lsb 0 xxxxx rd 11111 0 4 5 9 10 14 15 16-bit immediate data 15 0 msb lsb instruction format
37 destination: this field specifies the register the ut69r000 uses for the destination of the instruction. source: this field specifies the register the ut69r000 uses for the instruction source. immediate: if needed, this field contains the 16-bits of immediate data the ut69r000 requires for the long- immediate instruction. 9.3 operand addressing modes the ut69r000?s instruction set supports four basic addressing modes. all instructions require a source operand and a destination operand. the destination operand is a data register (rdn or xrdn) for all instructions, except the jump on condition (jc) instruction where the destination register contains a template for the jump condition tested for in the instruction. the source operand can be either a data register or immediate data for all instructions. the source operand can also be addressed in an indirect mode. in an indirect addressing mode, the source data register or the stack pointer contains an effective address. this address points to the memory location for operand data the ut69r000 uses during the current instruction execution. this type of memory addressing is only used with the load (lr), store (str), push, and pop instructions. destination addressing mode the destination operand is given explicitly for all ut69r000 instructions. the ut69r000 encodes a five-bit field, bits 9 through 5, in each instruction as follows: r0 -- 00000 xr0 -- 10000 r1 -- 00001 r16 -- 10001 r2 -- 00010 xr2 -- 10010 r3 -- 00011 r17 -- 10011 r4 -- 00100 xr4 -- 10100 r5 -- 00101 xr16 -- 10110 r6 -- 10110 r7 -- 00111 xr8 -- 11000 r8 -- 01000 r18 -- 11001 r10 -- 01010 xr10 -- 11010 r11 -- 01011 r19 -- 11011 r12 -- 01100 xr12 -- 11100 r13 -- 01101 xr18 -- 11101 r14 -- 01110 xr14 -- 11110 r15 -- 01111 acc -- 11111 nul -- 10111 source addressing modes the ut69r000 directly addresses the source operand by using one of three normal modes: (1) data register direct; (2) literal; and (3) immediate long data. data register direct when the ut69r000 uses the data register direct mode, the source operand is one of the data registers. the data register is explicitly stated for all instructions. the ut69r000 encodes a 5-bit field, bits 4 through 0, in each instruction as follows: r0 -- 00000 xr0 -- 10000 r1 -- 00001 r16 -- 10001 r2 -- 00010 xr2 -- 10010 r3 -- 00011 r17 -- 10011 r4 -- 00100 xr4 -- 10100 r5 -- 00101 xr16 -- 10101 r6 -- 00110 xr6 -- 10110 r7 -- 00111 r8 -- 01000 xr8 -- 11000 r9 -- 01001 r18 -- 11001 r10 -- 01010 xr10 -- 11010 r11 -- 01011 r19 -- 11011 r12 -- 01100 xr12 -- 11100 r13 -- 01101 xr18 -- 11101 r14 -- 01110 xr14 -- 11110 r15 -- 01111 reserved -- 10111 and 11111 literal when the ut69r000 uses the literal mode, the source operand is a 5-bit literal data value. the ut69r000 explicitly states this literal data value for the instructions. the ut69r000 encodes a 5-bit field, bits 4 through 0, in each instruction as follows: 0 -- 00000 -16 -- 10000 +1 -- 00001 -15 -- 10001 +2 -- 00010 -14 -- 10010 +3 -- 00011 -13 -- 10011 +4 -- 00100 -12 -- 10100 +5 -- 00101 -11 -- 10101 +6 -- 00110 -10 -- 10110 +7 -- 00111 - 9 -- 10111 +8 -- 01000 - 8 -- 11000 +9 -- 01001 - 7 -- 11001 +10 -- 01010 - 6 -- 11010 +11 -- 01011 - 5 -- 11011 +12 -- 01100 - 4 -- 11100 +13 -- 01101 - 3 -- 11101 +14 -- 01110 - 2 -- 11110 +15 -- 01111 - 1 -- 11111 immediate long when the ut69r000 uses the immediate long mode, the source operand is a 16-bit data value. the ut69r000 explicitly states this data for all instructions and encodes the 16-bit data in a second 16-bit instruction word (figure 32). the ut69r000 encodes the 5-bit field of the instruction source field, bits 4 through 0, as follows: imm -- 11111
38 special source operand addressing modes in addition to its three direct addressing modes, the ut69r000 also supports three modes of indirect addressing: (1) data register indirect; (2) stack pointer indirect; and (3) absolute. data register indirect when the ut69r000 uses the data register indirect mode, the source operand is a memory location addressed by the contents of the specified data register. the data register is explicitly stated for all instructions. this mode is only available on the lr, str, inr, and str instructions. the ut69r000 encodes a 5-bit field, bits 4 through 0, in each instruction as follows: r0 -- 00000 xr0 -- 10000 r1 -- 00001 r16 -- 10001 r2 -- 00010 xr2 -- 10010 r3 -- 00011 r17 -- 10011 r4 -- 00100 xr4 -- 10100 r5 -- 00101 xr16 -- 10101 r6 -- 00110 xr6 -- 10110 r7 -- 00111 r8 -- 01000 xr8 -- 11000 r9 -- 01001 r18 -- 11001 r10 -- 01010 xr10 -- 11010 r11 -- 01011 r19 -- 11011 r12 -- 01100 xr12 -- 11100 r13 -- 01101 xr18 -- 11101 r14 -- 01110 xr14 -- 11110 r15 -- 01111 reserved -- 10111 and 11111 stack pointer indirect when the ut69r000 uses the stack pointer indirect mode, the source operand is a memory location addressed by the contents of the stack pointer (sp) register. this mode is only available with pop and push instructions. the ut69r000 encodes a 5-bit field, bits 11 through 15, of each instruction when in the stack pointer indirect mode as follows: sp -- 10111. absolute when the ut69r000 uses the absolute mode, the source operand is the memory location addressed by the contents of the 16-bit immediate-data field accompanying the instruction. this mode is only available on the lr, str, inr, and otr instructions. the system programmer encodes the immediate data field as a second 16-bit instruction word. 9.4 data movement operations the ut69r000 places no restrictions on operand size during data movement. this means the size (byte, word, or long word) of the data in the source and destination do not have to match. the ut69r000 handles the data movement for all instructions. when a instruction specifies a word destination, a 16-bit result is always stored in the destination. if the instruction specifies a 5-bit literal source operand, then the ut69r000 sign-extends this source data to produce a 16-bit operand. if the instruction specifies a word-length source operand, there is no manipulation of the source data. if the instruction specifies a long-word source operand, the ut69r000 only retains the least significant 16 bits of the result. the ut69r000 truncates the most significant 16 bits of the result. when a instruction specifies a long-word destination, a 32-bit result is always stored in the destination. if the instruction specifies a 5-bit literal source operand, then the ut69r000 sign-extends this source data to produce a 32-bit operand. if the instruction specifies a word-length source operand, then the ut69r000 also sign-extends this source data to produce a 32- bit operand. if the instruction specifies a long-word-length source operand, there is no manipulation of the source data. when the system programmer specifies a byte instruction, the ut69r000 only stores eight bits of the result regardless of whether the instruction specifies a word or long-word destination register. operation code matrix the ut69r000 performs 30 basic operations, each with its own operation code. all the ut69r000?s operations are explicit, and are encoded in bits 14 through 10 of the instruction.
39 10.0 pin description legend for type and active fields: to = ttl output ti = ttl input tui = ttl input (pull-up) tdi = ttl input (pull-down) tto = three-state ttl output ttb = three-state ttl bidirectional co = cmos output osc = oscillator input to a pierce oscillator inverter ah = active high al = active low oscin 50 p14 osc oscillator and clock signals pin name pin number fltpk pga type active description oscout sysclk 51 52 p15 m14 co to oscillator input. a 50% duty cycle crystal-drive input for driving the ut69r000. oscillator output. a 50% duty cycle, single-phase clock output at the same frequency as the oscin input. system output. the buffered equivalent of the oscout signal. nui1 129 h2 ti processor status pin name pin number fltpk pga type active description nui2 nuo3 44 126 p12 g3 tui tto not used input 1. internal utmc use only. tie either high or low. not used input 2. internal utmc use only. tie low. not used output 3. internal utmc use only. nuo3 enter high impedance state when the ut69r000 is in the test mode ( test =0) -- -- -- nui3 45 n11 tdi -- not used input 3. internal utmc use only. tie low. 54 n15 tto processor state. this signal indicates the internal state of the ut69r000. a low on state1 indicates the ut69r000 is executing a new instructio n. a high on state1 indicates the ut69r000 is fetching an instruction. state1 enters a high-impedance state when the ut69r000 is in the test mode ( test =0). -- -- -- -- nui4 61 k15 tui not used input 4. internal utmc use only. tie high. -- state1 nu01 115 c3 tto not used output 1. internal utmc use only. -- nu02 113 a2 tto not used output 2. internal utmc use only.
40 118 d2 tto operand data bus arbitration pin name pin number fltpk pga type active description 119 120 e3 c1 tui tui bus request. the ut69r000 asserts this signal to indicate it is requesting control of the operand data bus (d0 - d15). brq enters a high-impedance state when the ut69r000 is in the test mode ( test = 0). bus grant. when asserted, this signal indicates the ut69r000 may take control of the operand data bus. it is tied to an internal pull-up resistor. bus busy. a bus master asserts this input to inform the ut69r000 that another bus master is using the operand data bus. it is tied to an internal pull-up resistor. operand data bus control pin name pin number fltpk pga type active description 121 112 e2 b3 tui tto data transfer acknowledge. this signal tells the ut69r000 that a data transfer has been acknowledged and the ut69r000 can complete the bus cycle. to assure the ut69r000 operates with no wait states, dtack can be tied low. dtack is tied to an internal pull-up resistor. memory or i/o. indicates whether the current bus cycle is for memory (high) or i/o (low). it remains in the high- impedance state during bus cycles when the ut69r000 does not control the operand buses. al 117 b1 tto al al al al bus grant acknowledge output. the ut69r000 asserts this signal to indicate it is the current bus master. when low, bgack inhibits other devices from becoming the bus master. when the ut69r000 relinquishes control of the bus, bgack enters a high-impedance state. 114 c4 tto read/write. indicates the direction of data flow with respect to the ut69r000. r/ wr high means the ut69r000 is attempting to read data from an external device, and r/ wr low means the ut69r000 is attempting to write data to an external device. r/ wr remains in a high-impedance state when the ut69r000 does not control the operand buses. continued on page 41. -- -- brq bgnt busy bgack dtack m/ io r/ wr
41 output enable instruction memory. this signal allows memory to place data on the instruction data bus. the store register to instruction memory (stri) instruction removes oe during the ck2 internal clock cycle. oe enters a high-impedance state when the ut69r000 is in the test mode ( test = 0). operand data bus control pin name pin number fltpk pga type active description 116 b2 tto data strobe. indicates valid data is on the operand data bus. the ut69r000 places ds in a high-impedance state when it does not control the operand buses. 42 r12 tto instruction memory control pin name pin number fltpk pga type active description 43 r13 tto write enable memory. this signal allows the ut69r000 to write to instruction memory. the store register to instruction memory (stri) instruction asserts we during the ck2 internal clock cycle. we enters a high-impedance state when the ut69r000 is in the test mode ( test = 0). al al continued from page 40. al uart control/timer clock uartin 127 f1 tui pin name pin number fltpk pga type active description uartout 128 g1 tto ah ah uart input. the ut69r000 receives serial data through this input. the serial data is stored in the ut69r000?s receiver buffer register (rcvr). it is tied to an internal pull-up resistor. uart output. the serial data stored in the ut69r000?s transmitter buffer register (txmt) is transmitted through this output. the uart output is fixed at 9600 baud, with eight data bits, odd-parity, and one stop bit. uartout enters a high-impedance state when the ut69r000 is in the test mode ( test =0). (9600 baud @ timclk = 12 mhz) continued on page 42. we oe ds
42 test (input). asserting this input places the ut69r000 into a test mode. in this mode, all the ut69r000?s outputs, except oscout and sysclk, enter a high- impedance state. when using test , the ut69r000 must have a mrst . mrst must be held active for at least one sysclk period after test is deasserted to assure proper operation (see figure 41b). test is tied to an internal pull-up resistor. timclk 53 l13 ti uart control/timer clock pin name pin number fltpk pga type active description di2 48 n12 tdi timer clock. this 12 mhz clock input generates the baud rate for the ut69r000?s internal uart. the input also provides the clock for the ut69r000?s two internal timers (timer a and timer b). discrete input 2. asserting this input sets bit 3 in the system status register bit 3 is read with the input register instruction (inr). tied to an internal pull-down resistor. (asynchronous input). test 46 p13 tui di1 49 n13 tdi -- discrete input 1. asserting this input sets bit 8 in the system status register. bit 8 is read with the input register instruction (inr). tie to a internal pull-down resistor. (asynschronous input). -- continued from page 41 al processor mode od0 104 b7 tto pin name pin number fltpk pga type active description od4 108 a4 -- output discrete bus (od(7:0)). these outputs reflect the status of bits 0 through 7 of the status/output discrete register. write to this register using output register instruction (otr). outputs enter a high- impedance state when the ut69r000 is placed in the test mode ( test = 0). od1 od2 od3 105 106 107 b6 c6 a5 od5 od6 od7 109 110 111 a3 b4 c5 --
43 memory parity (error). asserting this input indicates a machine error. bit 13 of the ut69r000?s fault register, is set when mchne2 is active. under no circumstances should mchne2 be tied in its active state. it is tied to an internal pull-down resistor. interrupt is not cleared via software until the negation of the input signal. mchne1 125 g2 tui interrupts/exceptions pin name pin number fltpk pga type active description 122 d1 tui system fault. this positive edge-triggered input sets bit 8 (mchne1) in the ut69r000?s fault register. under no circumstances should mchne1 be tied in its active state. it is tied to an internal pull-up resistor. interrupt is not cleared via software until the negation of the input signal. mchne2 bus time error. it is asserted when a bus error or a timeout occurs. during i/o bus cycles, an active bterr sets bit 10 of the fault register. during memory bus cycles, an active bterr sets bit 7 of the fault register. under no circumstances should bterr be tied in its active state. it is tied to an internal pull-up resistor. interrupt is not cleared via software until the negation of the input signal. 124 f2 tdi mprot 123 f3 tui ah memory protect fault. when asserted, it informs the ut69r000 that a memory-protect fault has occurred on the operand data bus. an access fault, a write-protect fault, or an execute-protect fault causes a memory-protect fault. if the ut69r000 is using the bus and mprot is asserted, bit 15 of the fault register (cpu fault) is set. if the ut69r000 is not using the bus and mprot is asserted, bit 14 of the fault register (dma error) is set. it is tied to an internal pull-up resistor. interrupt is not cleared via software until the negation of the input signal. al ah 56 m15 tui 62 j15 user interrupts. these interrupts are active on a negative- going pulse and each will set, when active, its associated bit in the pending interrupt register. the interrupts are maskable by setting the associated bits in the interrupt mask register. asserting mrst resets all interrupts. they are tied to an internal pull-up resistor. 57 58 59 60 k13 k14 j14 j13 63 h14 55 l14 tui al power fail (interrupt). asserting this input informs the ut69r000 that a power failure has occurred and the present process will be interrupted. this input sets bit 15 in the pending interrupt register. a power fail interrupt (bit 15) cannot be disabled or masked. it is tied to an internal pull- up resistor. 47 r14 tui al master reset. this input initializes the ut69r000 to a reset state. the ut69r000 must be reset after power (vcc) is within specification and stable to ensure proper operation. the system must hold mrst active for at least one period of sysclk to assure the ut69r000 will be reset. it is tied to an internal pull-up resistor. ah al bterr int0 int1 int2 int3 int4 int5 int6 int2 pfail mrst 61 k15 tui -- nui4 not used input 4. internal utmc use only. tie high.
44 a0 84 a14 tto operand buses pin name pin number fltpk pga type active description address bus - operand. when asserted, this bus is unidirectional and represents the operand address. the bus is in the high-impedance state when the ut69r000 does not control the bus. a15 is the most significant bit. the operand address enters a high-impedance state when the ut69r000 is in the test mode ( test = 0). d0 64 h15 ttb data bus - operand. this bidirectional data bus remains in a high-impedance state when the ut69r000 does not control the bus. d15 is the most significant bit. the operand data bus enters a high-impedance state when the ut69r000 is in the test mode ( test = 0). -- ra0 18 r2 tto instruction address bus. this unidirectional bus represents the address of the data in instruction memory. ra19 is the most significant bit. the address enters a high-impedance state only when the ut69r000 is in the test mode ( test = 0). a1 a2 a3 a4 a5 a6 a7 a8 a9 a10 a11 a12 a13 a14 a15 85 86 87 88 89 90 91 92 93 94 95 96 97 102 103 b12 c11 a13 b11 a12 c10 b10 b9 c9 a10 a9 b8 a8 a7 a6 d1 d2 d3 d4 d5 d6 d7 d8 d9 d10 d11 d12 d13 d14 d15 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 g15 f15 g14 f14 f13 e15 d15 c15 d14 e13 c14 b15 d13 c13 b14 -- instruction buses pin name pin number fltpk pga type active description ra1 ra2 ra3 ra4 ra5 ra6 ra7 ra8 ra9 ra10 ra11 ra12 ra13 ra14 ra15 19 20 21 22 23 24 25 26 27 28 29 30 31 36 37 p4 n5 r3 p5 r4 n6 p6 p7 n7 r6 r7 p8 r8 r9 r10 -- continued on page 45. ra16 ra17 ra18 ra19 38 39 40 41 p9 p10 n10 r11
45 pin name pin number fltpk pga type active description rd0 130 h1 ttb instruction data bus. this bidirectional data bus is the interface with the memory. rd15 is the most significant bit. the data bus enters a high-impedance state only when the ut69r000 is in the test mode ( test = 0). v 34 h3 +5 v dc power. power supply input. -- instruction buses pin name pin number fltpk pga type active description continued from page 44. rd1 rd2 rd3 rd4 rd5 rd6 rd7 rd8 rd9 rd10 rd11 rd12 rd13 rd14 rd15 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 j1 k1 j2 k2 k3 l1 m1 n1 m2 l3 n2 p1 m3 n3 p2 67 100 132 n9 g13 c7 j3 n8 h13 c8 power and ground v 1 33 66 99 reference ground. zero volts dc, logic ground. -- -- -- -- dd ss
46 11.0 absolute maximum ratings (1) symbol parameter limits unit dc supply voltage voltage on any pin dc input current storage temperature latchup immunity (2) -0.3 to +7.0 -65 to +150 v v ma ma maximum power dissipation maximum junction temperature thermal resistance, junction-to-case (3) 600 +175 10 mw -0.3 to v dd + .3 o c o c o c/w (referenced to v ss ) v dd v i/o i i t stg i lu p d t j q jc + 150 + 10 12.0 recommended operating conditions symbol parameter limits unit dc supply voltage temperature range 4.5 to 5.5 -55 to +125 v dc input voltage v v dd t c v in o c 0 to v dd notes: 1. stresses outside the listed absolute maximum ratings may cause permanent damage to the device. this is a stress rating only, and functional operation of the device at these or any other conditions beyond limits indicated in the operational sections of this specification is not recommended. exposure to absolute maximum rating conditions for extended periods may affect device reliability. 2. see discussion of test technique (figure 42). 3. test per mil-std-883, method 1012.
47 13.0 e l e c t r i c a l c h a r a c t e r i s t i c s v dd = 5.0v 10%; -55 c < t c < +125 c notes: 1. supplied as a design limit but not guaranteed or tested. 2. not more than one output may be shorted at a time for maximum duration of one second. 3. all inputs with internal pull-ups or pull-downs should be left open circuit, all other inputs tied low or high. test input pin asserted. 4. includes current through input pull-ups. instantaneous surge currents on the order of 1 ampere can occur during output swit ching. voltage supply should be adequately sized and decoupled to handle a large current surge. 5. double buffer output pins (i.e., ds , r/ wr , m/ io ). 6. functional tests are conducted in accordance with mil-std-883 with the following input test conditions: v ih =v ih (min)+20%,-0%; v il =v il (max)+0%,-50%, as specified herein, for ttl or cmos compatible inputs. devices may be tested using any input voltage within the above specifie d range, but are guaranteed to v ih (min) and v il (max). 7. radiation-hardened technology shall have a v ih pre-irradiation of 2.2v. symbol parameter condition minimum maximum unit v il low-level input voltage 6 ttl inputs osc inputs .8 1.2 v v v ih high-level input voltage 6 ttl inputs 7 osc inputs 2.0 3.6 v v i in input leakage current inputs without resistors inputs with pull-down resistors inputs with pull-up resistors v in = v dd or v ss v in = v dd v in = v ss -10 80 -900 10 900 -80 m a m a m a v ol low-level output voltage ttl outputs osc outputs i ol = 3.2ma i ol = 6.4ma note 5 i ol = 0.1ma 0.4 0.4 1.0 v v v v oh high-level output voltage ttl outputs osc outputs i oh = -0.4ma i oh = -0.8ma note 5 i oh = - 0.1ma 2.4 2.4 3.5 v v v i oz three-state output leakage current v o = v dd or v ss -10 -20 note 5 +10 +20 note 5 m a m a i os short-circuit output current 1,2 v dd = 5.5v, v o = 0v to v dd -100 -200 note 5 +100 +200 note 5 ma ma c in input capacitance f = 1mhz @ 0v 10 pf c out output capacitance f = 1mhz @ 0v 15 pf c io bidirectional i/o capacitance f = 1mhz @ 0v 20 pf i dd average operating current 1, 4 f = 16mhz, c l = 50pf f = 12mhz, c l = 50pf 75 50 ma ma q idd quiescent current note 3 1 ma
48 14.0 ac electrical characteristic figure 32a. typical timing measurements to data valid to high z to response to response to response input input input input input input input to high z to data valid to response input parameter h g f e d c b a t t t t t t t t symbol h g f e t t t t d b t t t c a t bus output out-of-phase output in-phase max il v min ih v input max ol v max ol v ol v min oh v min oh v min oh v max il v min ih v max *unless otherwise noted, all ac electrical characteristics are guaranteed by design or characterization. note: 50pf including scope probe and test socket. 90% figure 32b. ac test loads and input waveforms input pulses 10% 10% 90% < 2 ns < 2 ns 50 pf 3 v 0 v 5 v i ref (source) i ref (sink) v ref
49 41 45 38 55 42 38 41 38 38 35 45 33 -- 0 -- 0 -- 0 -- 0 0 0 0 0 ns ns ns ns ns ns ns ns ns ns ns ns ns 33 0 figure 33. i/o read cycle note: -- -- 0 26 oscin high to address invalid 134u t34t t34s t34r t34n t34m t34l t34j t34i t34k t34h t34g t34f t34b t34a valid data valid address oscin operand data operand address symbol parameter min max units t34a t34b data setup time data hold time t34f t34g t34h t34i t34j t34k t34l t34m t34n t34r t34s t34t t34u ns ns * * * * *guaranteed by test. * * * * * 16 mhz 55 57 50 73 51 50 54 50 50 37 54 39 -- 0 -- 0 -- 0 -- 0 0 0 0 0 42 0 -- -- 0 34 min max 12 mhz state1 ds r/ wr m/ io oscin low to state1 high oscin low to state1 low oscin low to ds inactive oscin low to ds active oscin high to ds inactive oscin low to ds high z oscin low to r/ wr active oscin low to r/ wr high z oscin low to m/ io low oscin high to m/ io high oscin low to m/ io high z oscin low to address valid
50 41 45 38 55 42 38 42 38 38 35 45 33 -- 0 -- 0 -- 0 -- 0 0 0 0 0 ns ns ns ns ns ns ns ns ns ns ns ns ns 33 0 figure 34. i/o write cycle 60 48 0 -- oscin high to address invalid oscin low to address valid t35u t35t t35s t35r t35n t35m t35l t35j t35i t35k t35h t35g t35f t35b t35a valid address oscin operand data operand address t35a t35b oscin low to data valid oscin high to data invalid (high z) t35f t35g t35h t35i t35j t35k t35l t35m t35n t35r t35s t35t t35u 54 0 t35v t35v ns ns ns valid data * * * * * * * * * * * symbol parameter min max units 16 mhz min max 12 mhz 55 57 50 73 51 50 51 50 50 37 54 39 -- 0 -- 0 -- 0 -- 0 0 0 0 0 42 0 80 64 0 -- 72 0 oscin low to state1 high oscin low to state1 low oscin low to ds inactive oscin low to ds active oscin high to ds inactive oscin low to ds high z oscin low to r /wr inactive oscin low to r /wr high z oscin low to m /io low oscin high to m /io high oscin low to m /io high z oscin high to r /wr high state1 ds r/ wr m/ io
51 41 45 38 42 38 42 38 38 35 45 33 -- 0 -- 0 -- 0 -- 0 0 0 0 ns ns ns ns ns ns ns ns ns ns ns ns 33 0 figure 35. operand portread cycle note: -- -- 0 26 oscin high to address invalid oscin low to address valid t36u t36t t36s t36r t36n t36l t36j t36i t36k t36h t36g t36f t36b t36a valid data valid address operand address t36a t36b * data setup time data hold time t36f t36g t36h t36i t36j t36k t36l t36n t36r t36s t36t t36u *guaranteed by test. ns ns * * * * * * * symbol parameter min max units 16 mhz min max 12 mhz 55 57 50 53 50 54 50 50 37 54 39 -- 0 -- 0 -- 0 -- 0 0 0 0 42 0 -- -- 0 34 oscin operand data oscin low to state1 high oscin low to state1 low oscin low to ds inactive oscin low to ds active oscin high to ds inactive oscin low to ds high z oscin low to r /wr inactive oscin low to r /wr high z oscin low to m /io high oscin low to m /io high z state1 ds r/ wr m/ io
52 41 45 38 42 38 42 38 38 35 45 33 -- 0 -- 0 -- 0 -- 0 0 0 0 ns ns ns ns ns ns ns ns ns ns ns ns 33 0 figure 36. operand port write cycle note: 60 48 0 -- t37u t37t t37s t37r t37n t37l t37j t37i t37k t37h t37g t37f t37b t37a valid address oscin operand data operand address t37a t37b * t37f t37g t37h t37i t37j t37k t37l t37n t37r t37s t37t t37u 54 0 t37v t37v ns ns ns valid data *guaranteed by test. * * * * * * * * * symbol parameter min max units 16 mhz min max 12 mhz 55 57 50 53 50 51 50 50 37 54 39 -- 0 -- 0 -- 0 -- 0 0 0 0 42 0 80 64 0 -- 72 0 oscin high to address invalid oscin low to address valid oscin low to data valid oscin low to state1 high oscin low to state1 low oscin low to ds inactive oscin low to ds active oscin high to ds inactive oscin low to ds high z oscin low to r /wr active oscin low to r /wr high z oscin low to m /io high oscin low to m /io high z state1 ds r/ wr m/ io oscin high to data invalid (high z) oscin high to r /wr high
53 33 0 ns notes: t38a 0 0 0 15 0 0 -- 10 0 10 10 33 41 44 -- -- 42 41 -- -- -- -- ns ns ns ns ns ns ns ns ns ns ns oscin operand data operand address 1 2 t38a t38b t38c t38d t38g t38h t38i t38j t38l valid data valid address t38b t38c t38d t38e t38f t38g t38h t38i t38j t38k t38l * * * * * symbol parameter min max units 16 mhz min max 12 mhz 42 0 0 0 0 15 0 0 -- 10 0 15 10 39 54 58 -- -- 53 55 -- -- -- -- t38e oscin low to state1 high oscin low to state1 low oscin high to brq low bgt setup time oscin low to bgack active dtack setup state1 ds r/ wr m/ io t38f t38k * guaranteed by test. 1. bgt must be active and busy high at this clock edge or wait states will occur. 2. to avoid wait states, dtack must be active here. dtack bgack bgnt brq busy oscin low to brq high bgt hold time oscin low to bgack high z dtack hold time busy setup busy hold time figure 37. dma no wait state must have bgnt active here for no wait states must have dtack active here for no wait states
54 ns ns ns ns ns ns ns ns ns ns t39j t39h t39g t39f t39e t39d t39c t39b t39a valid data valid address data instruction address instruction figure 38. stri command timing oscin t39a 0 0 0 0 0 0 0 -- -- -- 33 33 39 37 40 37 49 38 41 39 t39i note: t39b t39c t39d t39e t39f t39g t39h t39i t39j * *guaranteed by test. * * * * * * symbol parameter min max units 16 mhz min max 12 mhz 0 0 0 0 0 0 0 -- -- -- 39 42 52 46 50 49 65 50 55 52 state1 oe we oscin low to state1 low oscin low to state1 high oscin high to oe high oscin high to we low oscin low to address valid oscin low to oe low oscin high to we high oscin low to address high z oscin high to data valid oscin low to data high z
55 ns ns ns ns ns ns ns ns ns ns figure 39. lri command timing t40a 0 20 -- -- 0 0 0 0 0 0 0 -- 33 33 35 39 37 35 49 38 t40j t40i t40h t40g t40f t40e t40d t40c t40b t40a valid data valid address data instruction address instruction oscin t40b t40c t40d t40e t40f t40g t40h t40i t40j *guaranteed by test. note: * * * symbol parameter min max units 16 mhz min max 12 mhz 0 27 -- -- 0 0 0 0 0 0 0 -- 39 42 46 52 49 47 65 50 oscin low to state1 low oscin low to state1 high oscin high to oe low oscin high to we high oscin low to address valid oscin low to oe high oscin low to we low oscin low to address high z data setup time data hold time state1 oe we
56 figure 40. uart and timer a/b timclk timing t41b t41a ns ns timclk high time timclk low time t41b t41a timclk 24 -- -- 38 symbol parameter min max units 16 mhz min max 12 mhz 32 -- -- 50 mrst pulse width t 62 ns t figure 41a. master reset timing 83 ns t t 42a 42a 42b 42b symbol parameter min max units 16 mhz min max 12 mhz symbol parameter min max units 16 mhz min max 12 mhz 62 83 -- -- -- -- mrst mrst test mrst timing with test active figure 41b. master reset timing when test is active
57 latchup test configurations figure 42 shows the latchup test. v dd holds at +5.5 v dc , and v ss holds at ground. the device test is at 125 c. each type of i/o alternately receives a positive and then negative 150 ma pulse of 500 ms duration. the current is monitored after the pulse for latchup condition. to prevent burnout, the supply current is limited to 400 ma. the ut69r000ar has latchup immunity in excess of +150 ma for 500 ms. 500ms 500ms 150ma 0 -150ma pulse generator current meter power supply input or output gnd dut v dd figure 42. latchup test
58 15.0 packaging figure 43. 144-pin pingrid array notes: 1. package material: opaque ceramic. 2. true position applies at base plane (datum c). 3. true position applies at pin tips (datum c1). 4. all package finishes are per mil-prf-38535. 5. letter designations are for cross-reference mil-std-1835. 6. geometry of index mark cannot be an alpha or numeric symbol. 7. all v dd pads are connected to the power plane, die-attach, pad and external pins h3, n9, g13, and c7. 8. all v ss pads are connected to the power plane, die-attach, pad and external pins j3, n8, h13, and c8. pin usage: pga 113 - i/o 8 - power/ground 23 - no connect (b13, c2, c3, n14, p3, r1, d3, d4, m13, a15, e1, a1, a2, l2, n4, r5, b5, p11, a11, c12, e14, r15, l15)
59 notes: 1. all package finishes are per mil-prf-38535. 2. lead numbers 34, 67, 100, 132 are connected to the v dd plane. other leads can be used for v dd connections. 3. lead numbers 33, 66, 99, 1 are connected to the v ss plane. other leads canbe used for v ss connections. 4. the lid is connected to v ss. 5. letter designations are for cross-reference to mil-std-1835. figure 44. 132-lead flatpack (unformed leads) pin usage: fltpk 113 - i/o 8 - power/ground 8 - no connect (2, 32, 35, 65, 68, 98, 101, 131)
60 notes: 1 . all package finishes are per mil-prf-38535. 2. lead numbers 34, 67, 100, 132 are connected to the v dd plane. 3. lead numbers 1, 33, 66, 99 are connected to the v ss plane. other leads canbe used for v ss connections. 4. the lid is connected to v ss. 5. letter designations are for cross-reference to mil-std-1835. figure 45. 132-lead flatpack (non-conductive tiebar)
61 16.0 ordering information 69r000 microcontroller total dose: - = none (f) = 3e5 rads(si) (g) = 5e5 rads(si) (h) = 1e6 rads(si) (r) = 1e5 rads(si) lead finish: (a) = solder (c) = gold (x) = optional screening: (p) = prototype (c) = mil temp package type: (g) = 144-pin cpga (w) = 132-pin flatpack (gold only) (f) = 132-pin flatpack w/ncs access time: (12) = 12mhz operating frequency (16) = 16mhz operating frequency utmc core part number ut69r000 * * * * * notes: 1. lead finish (a, c, or x) must be specified. 2. if an ?x? is specified when ordering, part marking will match the lead finish and will be either ?a? (solder) or ?c? (gold). 3. military temperature range flow per utmc?s manufacturing flows document. devices are tested at -55 c , room temperature, and 125 c . radiation neither tested nor guaranteed. 4. prototype flow per utmc manufacturing flows. devices have prototype assembly and are tested at 25 c only. .lead finish is gold only. radiation is neither tested nor guaranteed. 5. 132 pin fp (package designator "w") only available with gold lead finish.
62 69r000 microcontroller: smd lead finish: (a) = solder (c) = gold (x) = optional case outline: (x) = 144-pin pga (y) = 132-pin flatpack (gold only) (z) = 132-pin flatpack w/ncs class designator: (q) = class q (v) = class v device type (01) = 12 mhz, rh microcontroller (02) = 16 mhz, rh microcontroller drawing number: 98552 total dose: (-) = none (h) = 1e6 rads(si) (g) = 5e5 rads(si) (f) = 3e5 rads(si) (r) = 1e5 rads(si) federal stock class designator: no options 5962 * 98552 01 * * * notes: 1. lead finish (a, c, or x) must be specified. 2. if an ?x? is specified when ordering, part number will match the lead finish and will be either ?a? (solder) or ?c? (gold). 3. 132 fp (package designator "y") only available with gold lead finish.

▲Up To Search▲

Price & Availability of UT69R00012FCCG

	To Download UT69R00012FCCG Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .